Electronic notebook system

ABSTRACT

An electronic notebook system is described comprising a housing, a computing device, wireless interfaces, antennas, sensors, a touch display configured to receive input via a stylus and/or human digit input, the stylus comprising a pressure and/or an inclination sensor, a microphone, camera, the system configured to provide a user condition interface, receive a user selection of a first user condition, provide an interface configured to receive user details, receive audible user details via the microphone, convert the audible user details received via the microphone to text, perform natural language processing to identify text keywords utilizing sentence segmentation, part-of-speech tagging, paraphrase recognition, and/or co-reference resolution, identify a condition based at least in part on the identified one or more keywords, dynamically generate an alert based at least in part on the identified condition, wirelessly transmit the alert to one or more destinations via at least a first wireless interface and antenna.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57.

BACKGROUND OF THE INVENTION Field of the Invention

This document relates to systems and techniques for electronicnotebooks.

Description of the Related Art

Conventional techniques for recording information include physicalnotebooks and simple electronic notebooks. However, such notebooks tendto be static in nature, recording manually entered information andmanually selected locations and then displaying such information asentered.

SUMMARY

The following presents a simplified summary of one or more aspects inorder to provide a basic understanding of such aspects. This summary isnot an extensive overview of all contemplated aspects, and is intendedto neither identify key or critical elements of all aspects nordelineate the scope of any or all aspects. Its sole purpose is topresent some concepts of one or more aspects in a simplified form as aprelude to the more detailed description that is presented later.

This document describes systems, processes and techniques that may beused to manage and process the recording, arrangement, text processing,word recognition, and/or review of information for or in an electronicnotebook such as a patient, psychiatrist, psychologist, or other medicalprofessional electronic notebook. For example, an electronic or digitalnotebook may optionally be managed by a hosted, secure, cloud basedsystem comprised of co-located and/or geographically distributed serversystems. The electronic notebook may be accessed over a network by oneor more users via one or more users. For example, the users may compriseone or more medical professionals (e.g., a psychiatrist, a familyphysician, a neurologist, a geriatrician, a therapist, etc.), a patient,a family member of the patient, a caretaker, etc. The electronicnotebook may enable two or more users to collaborate over a network withrespect to a patient's data and care. Optionally, a user of theelectronic notebook may issue an invitation to one or more other usersto collaborate.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described with reference to the drawingssummarized below. These drawings and the associated description areprovided to illustrate example aspects of the disclosure, and not tolimit the scope of the invention.

FIG. 1 illustrates an example architecture.

FIG. 2 illustrates an example user terminal architecture.

FIG. 3 illustrates an example software architecture for the example userterminal.

FIG. 3B illustrates an example process.

FIGS. 4A-4Z illustrate example electronic notebook user interface.

DETAILED DESCRIPTION

This document describes systems, processes and techniques that may beused to manage and process the recording, arrangement, text processing,word recognition, and/or review of, information in an electronicnotebook such as an electronic psychiatrist, psychologist, or othermedical professional notebook. For example, a notebook may optionally bemanaged by a hosted a secure, cloud based system comprised of co-locatedand/or geographically distributed server systems. The electronicnotebook may be accessed over a network by one or more users via one ormore user terminals (e.g., via a desktop computer, laptop computer,tablet, smart phone, networked television, network connected wearabledevice). By way of illustration the electronic notebook may be accessedas a web document via a browser and/or via a dedicated application(sometimes referred to herein as an “app”) installed and hosted on auser device. Optionally, some or all of the information processingdescribed herein may be performed via a system remote from the userterminal (e.g., by the cloud system), or optionally some or all of theinformation processing described herein may be performed by the userterminal. Optionally, some of the information processing describedherein may be performed via a system remote from the user terminal(e.g., the cloud system), and some of the information processingdescribed herein may be performed by the user terminal. The notebook mayinclude multiple sections, as discussed elsewhere herein. Optionally,the various electronic notebook sections may be organized using visualtabs.

Information between a user terminal and the remote system may besynchronized periodically and/or in response to an event (e.g., adetection of a change of data or receipt new data). By way of example,as will be discussed in greater detail herein, a system (e.g., the cloudsystem or a user device hosting an electronic notebook application) maygenerate, using information recorded or accessed via the electronicnotebook a health timeline for a patient. The health timeline may beupdated and the updates may be continuously or periodicallysynchronized.

The following example relates an electronic medical informationnotebook. Optionally, some or all of the information communicatedbetween a user terminal app (e.g., an electronic notebook app) and aremote system are transmitted securely to comply with certain regulatoryspecifications. For example, in order to ensure confidentiality ofmedication information, the medical information may be handled so as tocomply with the Health Insurance Portability and Accountability Act(HIPPA). For example, some or all of the information may be encryptedusing an encryption key.

The data may be secured by establishing a virtual private network (VPN)which establishes an encrypted transmission path between the userterminal and remote system. Optionally, Secure Sockets Layer (SSL), asecure transfer tunnel, may be used to encrypt data in transit betweenthe user terminal (e.g., the notebook app and/or browser) and the remotesystem. Optionally, some or all of the information may be stored on theuser terminal and/or the remote system using file encryption.Optionally, the encryption key may be stored physically separate fromthe data being encrypted (e.g., on different physical servers).

Optionally, access to notebook and/or other medical information isrestricted through user authentication. User authentication may bereceived in the form of a password and/or biometrics. For example, theuser terminal may be equipped with a fingerprint scanner which may beused to compare a fingerprint of someone attempting to access the userterminal and/or the notebook information with that of an authorizeduser. If there is a match access may be granted to the user terminaland/or notebook information. If the fingerprints fail to match, accessto the user terminal and/or notebook information may be denied. Anotherform of biometrics may be in the form of facial recognition. Forexample, the user terminal may be equipped with a camera which may beused to capture an image of someone attempting to access the userterminal and/or notebook information. Features extracted from the imagemay be compared to stored features of an authorized user. If there is amatch, access may be granted to the user terminal and/or notebookinformation. If the facial features fail to match, access to the userterminal and/or notebook information may be denied. Other authenticationtechniques may be used, such as voice recognition, secure fobs, and thelike.

Optionally, the users may comprise one or more medical professionals(e.g., a psychiatrist, a family physician, a neurologist, ageriatrician, a therapist, etc.), patients, patient family member, etc.The electronic notebook may enable two or more users to collaborate overa network. Optionally, a user of the electronic notebook may issue aninvitation to one or more other users to collaborate. For example, thecollaboration may relate to providing information with respect to apatient (e.g., past or recommended future treatments, changes in thepatient's life style, etc.). The invitation may be transmitted from theuser's terminal directly to the invitee's terminal, or the invitationmay be routed through the remote system to the invitee's terminal. Theinvitation may be provided to the invitee via a pop-up invitationdisplayed on the invitee's terminal (e.g., by the notebook app), via anSMS/MMS message, via an email message, via a notebook interfacepresented via a browser, etc.

A user (who may be patient, a medical professional, a family member, acaretaker, etc.) may utilize the electronic notebook to recordinformation regarding a patient/client (e.g., a patient with a mental orphysical illness, a patient with a physical or cognitive disability, apatient with a drug addiction issue, a patient with aging-relatedissues, etc.). The notebook may be used to record, process, andreproduce textual information, audio recordings, video recordings (whichmay include an associated audio recording track), photographs, medicaldiagnoses, x-rays, MRI scans, CAT scans, PET scans, medical testreports, medical treatment information, and/or other information. Forexample, textual information may include questions asked by a medicalprofessional of a patient and/or patient's family members, and responsesto such questions. Optionally, a given item of information recorded inthe notebook may be stored in association with metadata, such some orall of the following an identifier (e.g., name or user ID) associatedwith the user that recorded the information, an identifier indicatingthe user function (e.g., psychiatrist, patient, parent of the patient,child of the patient, etc.), geo-location information indicating thephysical location of the user when the user entered in the information(e.g., GPS location information received from the user terminal, such asa mobile phone), etc.

By way of example, the electronic notebook may be utilized to recordwhich medical professional a patient first encountered when admitted toan emergency room, other medical professionals the patient was treatedby in the emergency room, who performed which tests (e.g., x-rays, MRI,other scans, blood tests, etc.). By way of further example, theelectronic notebook may be used to list potential diagnoses, and toindicate when a given listed diagnosis has been determined to be nolonger a potential diagnoses.

The notebook may also be used to search for and/or display specialistsof a specified type that are in the geographic area of the patient(e.g., within a specified region, city, zip code, a specific number ofmiles from the patient's residence and/or from the device hosting thenotebook, etc.). For example, a search for specialists of a specifiedtype that are in the geographic area of the patient may be executed by asearch engine which will return a list of names that satisfy the searchcriteria. The specialist's name may be presented by the notebook app (ora browser) in the form of a link or in association with a link, whereinif the user clicks on the link, the notebook will access and displayadditional information regarding the specialist, such as the schoolsattended, the hospitals where the specialist interned, the hospitalswhere the specialist had a fellowship, the hospitals that the specialisthas admission privileges for, rating from one or more rating sources,etc.

The electronic medical information notebook may be configured to make iteasy for a patient or patient caretaker to access and understand themedical information, and to enter information, as well as appointments,records, and to do lists. As will be discussed, the electronic notebookmay include user interfaces configured to receive background andbiographical information for a patient, the ability to record verbaldiscussions at an appointment, the ability to convert voice-to-text, theability to generate lists of questions that are to be asked at anappointment, the ability to transmit the list of questions to one ormore recipients prior to the appointment, the ability to record referralinformation, the ability to receive and record contact information, theability to record office visit notes, the ability to share informationfrom the notebook with others, the ability to record treatment planinformation, the ability to record medication and prescriptioninformation, the ability to record medical procedure information, theability to record a diary/chronology of appointments, interventions,testing, etc., the ability to combine the diary with collectedbiographical, medical and clinical information, the ability tocommunicate with medical professionals (e.g., for the purposes ofproviding check-in information via video conferencing or messaging, textchats, VoIP, or otherwise), the ability to receive updates relevant to auser's area of concern, the ability to record, track, and analyzemedical insurance related matters, the ability to search for and accessresources by diagnosis, the ability to calendar events, such as medicalappointments.

FIG. 1 illustrates an example architecture. A notebook management system104 (which may be a cloud based system comprising one or more serversthat are co-located and/or that are geographically dispersed) may hostone or more applications that when executed cause a variety of theprocesses (e.g., the backend processes) described herein to execute.Optionally, the cloud system may include one or more Apache Hadoopclusters, optionally including a Hadoop distributed file system (HDFS)and a Hadoop MapReduce parallel processing framework. The system 104 maybe configured to process and store large amounts of data that would notbe effectively by conventional system. The system 104 may be configuredto process and store large amounts of structured data, unstructureddata, and/or semi-structured data. The data may relate to thepatient-related data (including sound and/or video recordings, scans,test results, contact information, calendaring information, biographicaldata, patient-related team data, etc.) disclosed herein. The clustersmay comprise master nodes (e.g., a name node, a job tracker, etc.), andslave nodes (e.g., data nodes, task trackers, etc.). A given data nodeserves data over a network using the distributed file system (e.g.,HDFS) protocol. The file system may utilize a TCP/IP layer forcommunication. The distributed file system may store large files acrossmultiple data node machines and may store copies of data on multiplehosts to enhance reliability and data availability.

With respect to the optional Hadoop implementation, other systems maysubmit tasks to the job tracker, which in turn, distributes the tasks toavailable task tracker nodes. Optionally, the job tracker may attempt todistribute a given task to a node in geographic proximity to the neededdata. While the foregoing example refers to Hadoop clusters and relatedcomponents, other distributed platforms may optionally be used inaddition or instead to process and store data, such as large amounts ofdata including structured, unstructured, and/or semi-structured data,(e.g., distributed platforms utilizing Bashreduce, Qizmt, Spark, DiscoProject, etc.).

The notebook management system 104 may communicate over one or morewired and/or wireless local and/or wide area networks (e.g., theInternet) 101 with one or more user terminals 118, 120. The userterminals 118, 120 may be wireless mobile devices, such as smart phones,tablets, laptops, wearables, or the like. The wireless mobile devicesmay optionally be equipped with wireless interfaces to communicate overWiFi, Bluetooth™, other local area wireless networks, other personalarea networks, cellular networks, or the like. The wireless mobiledevices may optionally be equipped one or more antennas connected torespective wireless interfaces. The antennas may be located within thehousing of the mobile device, and or on the housing surface of themobile device. The user terminals 118, 120 may be wired or wirelessnon-mobile devices, such as a desktop computer, a fixed or largenetworked television, a game console, or the like. The user terminals118, 120 may include a variety of sensors (e.g., sound, image,orientation, pressure, light, acceleration, and/or other sensors)configured to detect user input and interaction with the user terminals118, 120. The user terminals 118, 120 may include touch screensconfigured to display user interfaces and data and receive user inputvia touch. The user terminals may include physical keyboards. The userterminals 118, 120 may include one or more microphones to receive voicedata and commands, and one or more speakers to play audible content. Theuser terminals 118, 120 may include a camera configured to capture,record, and/or stream video data (which may be stored or streamed inassociation with captured audio data) to other systems, such as thenotebook management system 104. The user terminals 118, 120 may beassociated with the various user-types discussed herein, such aspatients, family members of patients, patient caretakers, medicalpersonnel, medical facilities, or other members of a support network.

The notebook management system 104 may communicate over one or morewired and/or wireless local and/or wide area networks 102 with one ormore remote servers or computing systems 106, 108, that may beassociated with medical service providers, one or more medical databases108, 110, or third party contact and calendar systems 112, 114. Thenetwork 101 and the network 102 may be the same or different networks.

FIG. 2 illustrates an example user terminal in the form of a tablet,phone, or laptop. In the example illustrated in FIG. 2, a user terminal200 includes various user input/output devices, such as atouchscreen/display 202, a microphone 204, a camera 206, physicalcontrols 208 (e.g., a power on/off control, a volume control, a homecontrol, etc.), a speaker 210, and/or other user input/output devices.The user terminal 200 may optionally include a haptic engine 211 thatprovides kinesthetic communication to the user (e.g., via vibrations ortaps, which may be used to confirm a user input or to provide anotification), an accelerometer 212 that measures acceleration in 2-3directions, and a gyrometer (e.g., a 3-axis gyroscope) 214 that measuresorientation in three axis. The user terminal 200 may be equipped with anexternal or integral physical keyboard, trackpad, joystick, electronicpen, and/or other input device.

The user terminal 200 may include one or more wireless and/or wiredinterfaces. For example, the user terminal 200 may include a WiFiinterface 216, a Bluetooth interface 218, a cellular interface 220, anNFC (near field communication) interface 222, and/or one or morephysical connectors 224 (e.g., a USB connector, a LIGHTING connector,and/or other connector). The user terminal 200 further comprises aprocessor device (e.g., a microprocessor) 230, volatile memory (e.g.,RAM solid state memory) and non-volatile memory (e.g., FLASH memory),and a power management device 234.

The electronic notebook application may be provided or accessed in theform of any application obtained/downloaded by the user terminal 200 viaa third party application store and/or via the notebook managementsystem 104. As described herein, the electronic notebook user interfacesmay include a variety of data entry fields. The fields may be populatedvia a keyboard, a stylus, via voice entry (provided via the microphone204) which may be converted to text via a voice-to-text module, or viafacial, limb, or figure gestures captured by the camera 206. Thekeyboard and/or stylus may be included with the user terminal 200. Thestylus may optionally be configured with a sensor to determine stylusinclination and/or a sensor to measure the pressure being applied to thestylus by the user. The pressure and inclination information may betransmitted to the user terminal 200 (e.g., via Bluetooth or otherwireless or wired protocol) and such information may be used to identifyuser issues as described elsewhere herein.

FIG. 3 illustrates an example, optional software architecture for atouch-enabled version of the example user terminal 200 illustrated inFIG. 2. The software architecture may include an operating system 350(e.g., GOOGLE ANDROID, APPLE iOS, MICROSOFT WINDOWS, APPLE OS, UNIX,LINUX, etc.), drivers 340 (e.g., display, touch sensor, speaker,microphone, memory, accelerometer, WiFi, Bluetooth, NFC, etc.),libraries 330 (e.g., SSL, Webkit, SQL, etc.), an application framework320, and applications 302. For example, the applications 302 may includea notebook application 304, a voice-text application 306, a calendarapplication 308, a messaging application 309, a camera application 310,a to-do list application 311, a browser application 312, a printerapplication 314 and/or other applications. A given application mayutilize another application as part of its operation. For example, thenotebook application 304 may call the voice-text application 306, thecalendar application 308, the messaging application 309, the cameraapplication 310, the to-do list application 311, the browser application312, and/or the printer application 314. Two or more of the applicationsmay be integrated into a single application.

The notebook application 304 may be configured to perform some or all ofthe functions and processes described herein.

When a user initially accesses the electronic notebook application togenerate a new electronic notebook, the electronic notebook applicationmay provide a user interface listing various medically-relatedconditions or categories. By way of non-limiting example, the conditionsmay include one or more of the following:

Autistic Spectrum Disorders

Developmental Disorders

Learning Disorders

Emotional or Psychiatric Disorders

Aging

Life altering Illness (e.g., cancer, Parkinson's, ALS)

Other

FIG. 4A illustrates an example user interface via which the user canselect a condition.

The application may access and/or generate an electronic notebooktemplate customized for the selected category. For example, the notebookmay include different questions and/or types of questions for differentcategories, and corresponding different information receiving fields.Examples of such templates will be discussed in greater detail elsewhereherein. Optionally, a free-form text field (e.g., the illustrated“Other” field) may be provided configured to receive a description of acondition that is not listed. Thus, for example, if a patient issuffering from a non-listed condition, a description of the condition,or related keywords, may be entered into the free-form field. Theapplication may utilize natural language processing (sometimes referredto as computational linguistics) to analyze and understand the textentry. Natural language processing may comprise the utilization ofmachine learning that analyzes patterns in data to improve the naturallanguage processing software's ability to understand the entry. Naturallanguage processing may utilize sentence segmentation, part-of-speechtagging (e.g., subject, object, modification, noun, adjective, number,etc.), parsing, named entity extraction (e.g., locating and classifyingelements in text into various categories such as the names of persons,organizations, locations, expressions of times, quantities, monetaryvalues, percentages, etc.), paraphrase recognition (determining whendifferent phrases or sentences have the same meaning), and/orco-reference resolution (finding all expressions that refer to the sameentity in a text). Fuzzy logic may be used to generate or select atemplate that includes suitable questions and fields.

Optionally, handwritten entries provided via handwritten touch entry(e.g., via a stylus or user finger/digit) may be analyzed to identifyuser stress. For example, the smoothness or jaggedness of thehandwritten entry may be identified (e.g., by identifyingdiscontinuities or abrupt horizontal inputs followed immediately byabrupt vertical inputs) to infer whether the user is undergoing stress.Similarly, stylus/finger pressure and inclination information may bereceived (e.g., via a wireless interface), stored and analyzed toidentify user stress (e.g., pressure or inclination angle above arespective threshold may indicate stress).

The electronic notebook may include fields for receiving content and/ordemographic information of a patient. For example, as illustrated inFIG. 4B, the fields may include name, address, biological gender, genderidentification, date of birth, and/or diagnosis. Other example fieldsinclude fields configured to receive an indication as to whether thepatient is a primary user of the electronic notebook, and if not, anindication/name as to who is the primary user of the notebook, and theprimary user's relationship to the patient (e.g., parent, child,sibling, caretaker, physician, etc.). Still other example fields mayinclude a field to receive an identification as to who is living withthe patient and their relationship to the patient (e.g., parent, child,sibling, caretaker, friend, etc.), an identification as to who attendsto the patient on a daily or regular basis, an indication as to whetherthere are family members or staff that assist with the patient, etc.

As noted above, a health timeline may be generated. The health timelinemay include some or all of the biographical information collected by theapplication. The health timeline may be utilized to help provide anoverview of the patient's issues and potential relationships betweensuch biographical information and the patient's medical issues and/ortreatment. Thus, the health timeline may provide a quick overview of thepatient and the patient's medical history. FIG. 4C illustrates anexample health timeline data collection introduction.

Example questions and response fields presented by the application willnow be discussed. Some or all of the collected data may be used togenerate a health timeline.

Autistic Spectrum Disorder (see, e.g., FIG. 4D): If the selected patientcategory is Autistic Spectrum Disorder, the application may query theuser to indicate the patient's relationship with user of the electronicnotebook (e.g., the patient herself/himself, parent, spouse, child,other family member (e.g., sibling, uncle, aunt, niece, nephew, etc.),other). The application may further query the user regarding thepatient's diagnosis, the patient's age when first diagnosed, whetherthere are family members with the same diagnosis, and if so, who aresuch family members (e.g., their name and/or relationship to thepatient). The application may additionally query the user as to whetherthere are other family members with another developmental orpsychological diagnosis, and if so, who are such family members (e.g.,their name and/or relationship to the patient), and what is theirdiagnosis. The application may also query the user as to who does thepatient live with, who takes the patient to medical appointments, whoholds the patient's medical information (e.g., who knows whatmedications, the patient is on, the course of their diagnosis, thepatient's treatment history, etc.). The application may query the useras to whether an IEP (Individual Educational Plan) been generated forthe patient, and if so, when and by what entity. With respect toeducation, the application may query the user as to whether there is aneducational specialist that works with this patient (and is so, who),whether the patient is participating in an educational program or study,and if so, what education program or study, and what level (e.g., whatgrade).

Developmental Disorders/Learning Disorder (see, e.g., FIG. 4E): If theselected patient category is Developmental Disorders/Learning Disorder,the application may query the user to indicate the patient's diagnosis,the patient's age when first diagnosed/when the diagnosis was firstmade, who is the primary treatment professional for the patient, arethere any other family members with this or similar diagnosis, has anIEP (Individual Educational Plan) been generated for the patient, and ifso, when and by what entity, and what is the patients learningenvironment (what education program is the user participating in).

Emotional or Psychiatric Disorder (see, e.g., FIG. 4F): If the selectedpatient category is Emotional or Psychiatric Disorder, the applicationmay query the user to indicate the patient's diagnosis, the patient'sage when first diagnosed/when the diagnosis was first made, does thepatient have any other diagnosis, does the patient have any chemicaldependency issues, has the patient been dually diagnosed (diagnosed witha mental illness and a comorbid substance abuse problem), and/or has thepatient been in a dual diagnosis treatment or addiction treatment and ifso provide details. The application may also ask if the patient has everbeen hospitalized, either voluntarily or involuntarily, if any of thepatient's family members received this diagnosis, and if so that detailsbe provided. The application may additionally ask if the patient iscurrently in treatment with emotional health professionals, whether thepatient taking medication, and if so, what medication.

Aging (see, e.g., FIG. 4G): If the selected patient category is aging,the application may query the user to indicate who is the specialistcurrently treating/seeing the patient, what is the reason for the visitto the specialist, whether any tests will be conducted by thespecialist, and if so, the test types that will be conducted (where thetest results will be forwarded to the referring primary physician forreview). The application may also ask the user to indicate whethermedication being prescribed is being prescribed for the patient, and ifso, the types of medication and who will be following up with thepatient to ensure that the patient is taking the medication, and theeffect of the medication on the patient. The application mayautomatically notify the patient's referring primary physician and/orteam leader (as discussed elsewhere herein) in response to detectingthat the user has indicated that the patient has been newly prescribedmedication. The application may also query the user to enter contactinformation (name, phone number, email, address, etc.) and specialty ofany medical specialist the patient is seeing. As described elsewhereherein, such information may be automatically added to contact datastore associated with the application.

Optionally, if the user fails to enter information in response to agiven query, the application will automatically notify the patient'sprimary physician and/or team leader of such failure and may prompt theprimary physician (e.g., via an email, text message, phone call, alertwithin an electronic notebook interface, or otherwise) to follow-up.

Life Altering Illness (see, e.g., FIG. 4H): If the selected patientcategory is life altering illness, the application may query the user toindicate the patient's relationship with the user of the electronicnotebook (e.g., the patient herself/himself, parent, spouse, child,other family member (e.g., sibling, uncle, aunt, niece, nephew, etc.),other). The application may also query the user to indicate thepatient's diagnosis, when the diagnosis was given, who gave thediagnosis, has a treatment plan been established, who monitors thetreatment plan, how does the patient get to and from appointments (e.g.,does the patient drive herself, does a family member, friend, caretakerdrive the patient, does the patient take a car service, etc.), and who(if anyone) accompanies the patient to doctor appointments.

The electronic notebook may optionally include instructions with respectto voice recording appointments and regarding preparing questions forthe appointment (see, e.g., FIG. 4I).

The electronic notebook may optionally include fields of user and/orpatient questions for the medical service provider (see, e.g., FIG. 4J).Thus, such questions may be entered prior to the appointment, avoidingreliance on fallible memory with respect to questions or areas ofconcerns.

The electronic notebook may include a record control, which whenactivated, enables video and/or audio of a given appointment to berecorded by the device hosting or accessing the application (see, e.g.,FIG. 4J). The recorded content of the appointment enables the user,patient, and/or other medical professionals to later review the recordedappointment without requiring that the user, patient, and/or othermedical professional manually write or type in notes during theappointment. The recording of an appointment will reduce user and/orpatient stress during the appointment as there will be no need tomanually take notes. For example, because the recorded appointment mayinclude information on new or existing treatment modes (e.g.,medication, exercise, physical therapy, et.), the electronic notebookcan generate and/or provide user interfaces textually providing suchinformation, and may further generate and/or provide follow-up userinterfaces that can be used to receive and record follow-up informationindicating whether the patient is taking the medication, following otherinstructions provided by the doctor/specialist, the patient's physicalcondition and health, etc.

The spoken voice captured via the recording may be converted to textusing a voice-to-text module. The voice-to-text module may perform theconversion using one or more of pattern matching, (where a spoken wordis recognized in its entirety), pattern and feature analysis (where aspoken word is broken into bits and recognized from key features, suchas the vowels it contains), language modeling and statistical analysis(in which a knowledge of grammar and the probability of certain words orsounds following on from one another is used to speed up recognition andimprove accuracy), and/or neural networks (trainable brain-like computermodels that can reliably recognize patterns, such as word sounds, aftertraining).

A characterization module (which may be included in the app and/or theremote system) may be utilized to recognize certain types of content inthe recorded content (e.g., in the voice recording or the text filegenerated by the voice-to-text module). For example, thecharacterization module may identify certain keywords in a given phrase,sentence or series of sentences that correspond to certain subjectmatter. The corresponding identified subject matter may then be selectedand inserted into a corresponding field/section in the electronicnotebook for convenient and organized viewing by a user. Optionally, thecomplete speech-to-text file for a given recording may beinserted/accessible from a calendar, where the calendar includes alisting of past and future appointments, an indication as to whetherthere are one or more appointment recordings, and any associated otherfiles (e.g., test reports (e.g., drug tests, blood tests, psychiatricreports, orthopedic reports, etc.), prescriptions, imaging reports(e.g., x-ray, MRI, CAT scan, etc.). An example subject matter mayinclude professional recommendations, and example subset subject matterof professional recommendations may include recommended tests,medications, interventions, etc. Thus, for example, if thecharacterization module identifies certain words or phrases that aretypically associated with professional recommendations, such as“recommend” (or variations thereof, such as “recommended” or“recommends”), “prescribe” (or variations thereof, such asprescription), “dose” (or variations thereof, such as “dosage”), “refer”(or variations thereof, such as “referral”), “test” (or variationsthereof, such as “tests, or equivalents, such as “exams”, etc.), inspect(or variations thereof, such as “self-inspect”), “avoid,” “take”,“inject”, etc., associated sentences or phrases may be categorized asrecommendations. Another example subject matter may include patientconcerns. Thus, for example, if the characterization module identifiescertain words or phrases that are typically associated with patientconcerns, such as “problem,” “worry”, “concern,” “anxiety,” “nervous,”“agitated,” “uneasy”, or derivatives or equivalents, associatedsentences or phrases may be categorized as concerns.

Another example subject matter may include patient history. Thus, forexample, if the characterization module identifies certain words orphrases that are typically associated with patient history, such as “ageat first diagnosis”, “other family members with the same diagnosis,”“other diagnosis,” “other family members with another developmental orpsychological diagnosis”, “the patient has been hospitalized,” “takingmedication,” “been prescribed,” “in treatment,” other patient historyquestions or information, discussed herein, etc.,” derivatives orequivalents, associated sentences or phrases may be categorized aspatient history. As similarly discussed above with respect to textentries, natural language processing may be utilized to analyze andunderstand the text file generated by the voice-to-text module.

If a professional recommendation is identified (e.g., a test, ormedication, or intervention), it may be automatically added to a to-dolist/reminder. The to-do list may be accessed via a menu entry availableon some or all pages of the virtual notebook. The to-do list mayoptionally be presented each time a user opens the app. Once therecommendation has been implemented (e.g., the test has been performed,the patient has started taking the medication, etc.), the patient,caretaker, or medical professional, can mark the to-do item ascompleted/implemented. Optionally, items marked as completed/implementedmay be moved from a viewable active to-do list to acompleted/implemented to-do list.

Optionally, the virtual notebook may include an appointment listfunction. The list may enable a user (e.g., a patient or patientcaretaker) to generate a list of questions to ask a medical professionalat an upcoming appointment. For example, the user can enter a name ofthe medical professional, the medical professional specialty, theappointment date. Optionally, the user can send the list to the medicalprofessional prior to the appointment so that the medical questions canbe prepared to answer the questions. Optionally, the application willautomatically issue a reminder (e.g., via a pop-up alert, an SMS/MMSmessage, an email message, etc.) to the user a certain period of time(e.g., a certain number of days) prior to the appointment to send thelist to the medical professional. The list may be entered via akeyboard, a stylus, or via voice entry which may be converted to textvia the voice-to-text module. Optionally, on the day/time of theappointment, the application may pop-up the list to ensure the user doesnot forget to ask the medical questions. The medical professional'sresponses can be recorded, converted to text, and entered in thenotebook underneath or otherwise in association with the correspondingquestions. The response is determined to correspond to a recommendation,it may be entered into the to-do list as similarly discussed above.

The electronic network may also include a referral user interface (see,e.g., FIG. 4K). The referral user interface may include fields used torecord information regarding a medical-related referral to a medicalprofessional. The fields may be populated via a keyboard, a stylus, orvia voice entry which may be converted to text via the voice-to-textmodule.

The following are example referral user interface questions which areassociated with corresponding user entry fields:

-   -   Who is the referral source (e.g., the name of a medical        professional that provided the referral);    -   What is the name of the referral;    -   What is the medical specialty of the referral;    -   What is the goal of the referral;    -   Is there a report or test to be completed or conducted by the        referral.

Optionally, the referral contact information (e.g., phone number, emailaddress, physical address, fax number, Skype® name, officeassistant/associate, specialty) etc.) is automatically added to acontact database of the user. Optionally, other information, such as thename of the referral source, dates of appointments/visits, etc. may berecorded in the referral contact record, such as that illustrated in thecontacts user interface illustrated in FIG. 4L. Optionally, theapplication prompts the user to approve adding the referral contactinformation to the contact database prior to the addition to the contactdatabase. Optionally, other relevant electronic notebook user interfaces(e.g., corresponding calendar appointment entries) are automaticallyaugmented with some or all of the referral's contact information.

The electronic network may also include an office visit user interface,such as the example user interface illustrated in FIG. 4M. The referraluser interface may include fields used to record information regarding amedical-related office visit. The fields may be populated via akeyboard, a stylus, or via voice entry which may be converted to textvia the voice-to-text module.

The following are example office user interface fields:

Name of provider/medical professional;

Date of office visit;

Recommendations from office visit;

Referrals provided at office visit;

Follow-up appointments needed;

Impressions of office visit.

The electronic network may also include “wall” user interface, anexample of which is illustrated in FIG. 4N. The wall user interface isconfigured to receive from and share with others in similar situations(e.g., having similar diagnosis). The wall user interface may includethe following example fields:

A search field configured to receive a user search query enabling a userto search through wall postings. For example, the user search query maybe submitted to a search engine which will identify and return postingsand/or links to postings that match the search query, which may be inturn displayed via the user terminal (e.g., via the notebook app or abrowser interface).

A search filter user interface enabling the user to select predefinedsearch filters to define a search or to narrow search results. Forexample, the filters may include one or more diagnosis or conditions(e.g., drug addiction, aging, dementia, special needs, seizure disorder,Parkinson's, cancer, hyperactivity, etc.), one or more treatments (e.g.,anti-anxiety medication, chemotherapy, blood pressure medication,antiviral medications, anti-seizure medication, etc.), treatment sideeffects (e.g., sleeplessness, nausea, anxiety, dizziness, etc.),favorites (which will cause posts that have been marked as favorites bythe user or that are posted by a posting user that has been marked as afavorite), etc.

A posting field via which the user can post information, experiences,opinions, resources, etc. There may be a field for posting what the userfound helpful or useful with respect to the patient's medical issue, andthere may a field for posting what the user did not helpful or useful.

A tag field via which the user can assign one or more tags to the user'spost to make it easier for other users to search for and access thepost. For example, the tags may include some or all of the filter termsand/or other terms.

The wall user interface may also include one or more controls, such a“favorite” control via which enables a user to indicate that certainposts or certain posting users are favorites.

FIG. 4O illustrates an example treatment plan user interface via whichtreatment plan information may be populated. For example, the treatmentplan may include fields that are automatically populated usinginformation recorded during an office visit and converted from voice totext, and/or the fields may be manually populated using a keyboard,stylus, or otherwise. The treatment plan user interface may include afield that specifies who is in charge of monitoring the treatment plan.For example, a physician (including name and specialty) can bespecified, a family member (including name and relationship) can bespecified, a treatment professional (including name and specialty) canbe specified, a team leader can be specified, etc. The treatment planmay include a field which indicates whether there is a prescribedfollow-up schedule, and details on any follow-up schedule. For example,the follow-up details may include follow-up dates, follow-up frequency,follow-up intervals, follow-up channel (e.g., via phone, office visit,laboratory tests, etc.), and an identification of a treatmentprofessional designated to ensure that the follow-up occurs.

The notebook application or the remote system can track the prescribedfollow-up dates, follow-up frequency, and/or follow-up intervals, andwhen a determination is made that it is time for a follow-up (e.g., theday of the scheduled follow-up or a specified number of days prior tothe scheduled follow-up), an alert may be generated and provided to thepatient, designated caregiver, significant other, specified physician,team leader, and/or other designated person to follow-up. The alert maybe presented via a notification transmitted to the recipient's device(e.g., via a pop-up alert, a text message, an MMS message, an email, acalendar alert, or otherwise).

The application or remote system may detect that follow-up has notoccurred (e.g., by detecting that the alert recipient and/or patient hasnot confirmed via a user interface that the follow-up occurred). If itis detected that the follow-up has not occurred in the prescribed timeframe, then the treatment professional attached to the follow-up will bealerted to check in with the patient and/or those who were designated toperform the follow-up.

FIG. 4P illustrates an example medication and medical procedure userinterface via which medication and medication procedure information maybe populated. A separate medication record may be created for eachmedication. For example, the medication user interface may includefields which may be populated with the name of the medication, the nameand specialty of the person that prescribed the medication, the goal ofthe medication, when a prescription for the medication was first order,the medication protocol (e.g., how is medication taken (pill, liquid,injection, etc.), how often the medication is to be taken, etc.), thename of the person that is responsible for following up on theefficacy/effectiveness of the medication, according to the prescriber,how long will it take to determine if the medication is having thedesired results, the medication side effects, are there any medicationsor foods that are to be avoided while taking the medication, themedication follow-up plan, and/or other information.

A separate medical procedure record may be created for each medicalprocedure. For example, the medical procedure user interface may includefields which may be populated with the names of the medical proceduresthat have been performed for the patient, the date of a given procedure,the name of the person that ordered the procedure, where was theprocedure performed, who performed the procedure an indication as towhether the user has a copy of the procedure results, if the user doesnot have a copy of the procedure results then name of the person thathas a copy of the procedure results, and/or other information.

FIG. 4Q illustrates an example clinical/therapeutic treatment userinterface via which clinical/therapeutic treatment information may bepopulated. A separate record may be created for eachclinical/therapeutic treatment. For example, the medical procedure userinterface may include fields which may be populated with an indicationas to whether the patient is seeing a therapist, psychiatrist orpsychologist, and if so, their name. The user interface may furtherinclude fields which may be populated with a treatment frequency, anindication as to whether another family member is seeing therapist,psychiatrist or psychologist and if so, the name and treatmentfrequency. The user interface may further include fields which may bepopulated with the types of psychological testing that has beenperformed on the patient.

FIG. 4R illustrates an example diary/chronology user interface. Thediary section of the notebook may be utilized to record and view anongoing chronology of appointments, interventions, testing, etc., andassociated dates,

The diary may be updated (e.g., via voice entry, a keyboard, stylus, orusing information recorded via another section of the notebook) witheach new appointment, intervention, test, etc. Optionally, the diarywill sequentially present dates on which an event occurred, and briefdescription of the event (e.g., “appointment with neurologist”,“prescription of Felodipine to control blood pressure,” “MM scan”,etc.). Optionally, an additional information control (e.g., a “more”control) may be provided which when activated by a user will causeadditional information regarding the event to be accessed and displayed.For example, the additional information may be accessed from anothernotebook section. By way of illustration, the information may beaccessed from the office visit section, the treatment plan section, themedication section, the clinical/therapeutic treatment section, and/orother section. There may be separate diaries for different on-goinghealth concerns.

FIG. 4S1 illustrates an example health timeline generated by the systemusing collected data described herein. The generated health timeline maybegin at a certain point in time, such as a significant biological date(e.g. date of birth of the patient), and may indicate, in chronologicalorder, the dates each diagnosis was made and the date of each medicalintervention/treatment. Optionally, the health timeline may be updatedin real time in response to the receipt of new or updated diagnosisand/or treatment data. Optionally, new or updated information may beemphasized (e.g., by color, font, icon, etc.) for a determined orspecified period of time (e.g., 7 days, 1 month, 180 days, or other timeperiod). Optionally, the health timeline may be configured so that it islinear (where a unit of distance is equal to a set amount of time) or isnon-linear in terms of time. For example, the timeline may be alogarithmic where the timeline is laid out according to a logarithmicscale such that the time axis itself is plotted logarithmically so thatmore recent time periods (and associated diagnosis and/or treatmentdata) may be provided with relatively more space on the timeline thanolder time periods.

Optionally, the health timeline may be zoomable to focus on a particulartime period and to display additional entries for a given time period.For example, the timeline may be zoomable via a user interface thatenables the user to use a lasso or other tool to indicate a beginningand end portion of the timeline that is to be zoomed. Optionally, inaddition or instead, the user interface enables the user to numericallyspecify a numerical zoom factor and/or to use a touch interface tostretch/zoom out a given portion of the health timeline by touching oneend of the portion with a thumb, touching the other end of the portionwith a finger, and then moving the thumb and finger apart. Optionally, aselected portion of the health timeline may be generated and displayedat a higher time resolution at the same time the original timeline isdisplayed at the original resolution, as illustrated in FIG. 4C.Optionally, a given timeline entry may be selectable (e.g., clickable),wherein in response to a user selection, additional informationregarding the selected entry is accessed and displayed (e.g., for amedical test, the test results and/or scans may be accessed anddisplayed).

FIGS. 4S2 and 4S3 illustrates an example master combined introductionuser interface and timeline user interface. The master/combined userinterface merges some or all of the information from the Biographical,Medical, Clinical, Therapeutic, Diary, and/or other sections of thenotebook into a unified timeline that lists the events, treatments, andother information with associated dates and/or times. Thus, the mastercombined user interface provides an overall snapshot for the patient.Optionally, the master combined user interface may be similar inappearance to the health timeline, with additional information. Themaster combined user interface may include all or a subset of theinformation included in the health timeline.

The generated master combined user interface may include a timeline thatbegins at a certain point in time, such as a significant biological date(e.g. date of birth of the patient), and may indicate, in chronologicalorder, significant biographical information (e.g., where and when thepatient went to school, when the patent was married, how many childrenthe patient has and when each child was born, when and where the patienthas been employed, whether the patient's parents are still alive, and ifnot when a given parent died, etc.), diagnosis dates, medicalintervention/treatment dates, diary entries, listings of appointmentswith medical professionals (e.g., therapist, psychiatrist orpsychologist, and their name), treatment frequency, psychological and/orother patient testing, etc. Optionally, the master combined userinterface may be updated in real time in response to the receipt of newor updated biographical, medical, clinical, therapeutic, and/or diarydata. Optionally, new or updated information may be emphasized (e.g., bycolor, font, icon, etc.) for a determined or specified period of timeafter being received or initially displayed (e.g., 7 days, 1 month, 180days, or other time period). Optionally, the master combined userinterface timeline may be configured so that it is linear (where a unitof distance is equal to a set amount of time) or is non-linear in termsof time. For example, the timeline may be a logarithmic where thetimeline is laid out according to a logarithmic scale such that the timeaxis itself is plotted logarithmically so that more recent time periods(and associated diagnosis and/or treatment data) may be provided withrelatively more space on the timeline than older time periods.

Optionally, the master combined user interface timeline (and/or thehealth timeline) may be zoomable to focus on a particular time periodand to display additional entries for a given time period. Optionally,the user interface enables the user to numerically specify a numericalzoom factor and/or to use a touch interface to stretch/zoom out a givenportion of the timeline by touching one end of the portion with a thumbor other digit, touching the other end of the portion with a finger orother digit, and then moving the thumb and finger apart. Similarly, theuser interface may enable the user to zoom in on a given portion using apinch gesture, by touching one end of the portion with a first digit(e.g., a thumb), touching the other end of the portion with a seconddigit (e.g., a finger), and then moving the two digits (e.g., thumb andfinger) together. As similarly discussed above with respect to thehealth timeline, optionally, the timeline may be zoomable via a userinterface that enables the user to use a lasso or other tool to indicatea beginning and end portion of the timeline that is to be zoomed.Optionally, a selected portion of the timeline may be generated anddisplayed at a higher time resolution at the same time the originaltimeline is displayed at the original resolution, as illustrated in FIG.4S. Optionally, a given timeline entry may be selectable (e.g.,clickable), wherein in response to a user selection, additionalinformation regarding the selected entry is accessed and displayed(e.g., for an appointment, a calendar entry may open showing the time,date, location and/or other information).

FIG. 4T illustrates an example check-in user interface. The check-inuser interface facilitates communication between a user/patient and atreating professional. For example, the check-in user interface mayenable the user to provide updates on how the patient is doing. Thetreatment professional may also designate, via an authorization userinterface, support staff to receive the check-in information onpatient-by-patient basis, for all patients, or for specific classes ofpatients (e.g., information for adult patients, but not minors). In theevent that support staff is designated or authorized to assist thetreatment professional in the patient communication, the appropriatemembers of the support staff may also added to the notebook contact datastore in association with an indication as to which treatmentprofessional they are associated with.

The check-in user interface may include the following selectable optionswith respect to who is performing the check-in: Patient; or SignificantOther/Care Giver/Family Member. The selected option may be communicatedto the check-in information recipient so that the recipient will knowwho is providing the check-in information. The check-in frequency may bescheduled and the schedule may be determined based at least in part on arecommendation of the treating professional. The schedule may be enteredinto the notebook calendar (e.g., via the treatment plan section of thenotebook). The notebook will then provide an alert or cue (e.g., via apop-up alert, an SMS/MMS message, an email message, etc.) to one or moredesignated alert recipients (e.g., the patient, the patient'ssignificant other, child, caretaker, etc.) that it is time to check-in.The alert may be provided on the scheduled check-in day and/or a certainperiod of time (e.g., a certain number of days) prior to the check-inday. Check-in may also be performed in an unscheduled manner (e.g.,based on perceived need by the patient).

A field may be provided configured to receive free-form text via whichthe check-in information may be provided. Natural language or keywordprocessing may be utilized to identify (e.g., with a certain likelihoodpercentage) that words or phrases used in the information providedduring the check-in (e.g., by the patient, significant other, caregiver,family member), or slurred or unintelligible speech, indicate anelevated or immediate need for attention. If the processing detects suchan elevated or immediate need for attention, an alert may be provided tothe treating professional (e.g., via a pop-up alert, an SMS/MMS message,an email message, etc.), where the alert may indicate that the check-ininformation needs to be urgently reviewed, and that the patient may needimmediate attention. For example, words and phrases that indicateurgency may include some or all of the following terms and/or otherterms: hopeless, worthless, suicidal, anxious, depressed, afraid,helpless, afraid, out-of-control, gun, knife, rage, violent, etc. By wayof further example, urgency may be indicated if system or app detectsthat the information provided via the check-in user interface isunintelligible or the speech (e.g., slurred speech) or text patternsindicate that the user is engaging in substance abuse (e.g., of drugs oralcohol) or is suffering a stroke. The alert may be dynamicallygenerated and composed to include the keywords/terms that triggered thealert, and/or may indicate that unintelligible/slurred speech wasdetected. Speaker-adaptive, continuous speech recognition may beutilized in converting speech to text.

Optionally, if the app or system detects that the patient has notchecked at the specified interval or schedule, an alert may be generatedand provided to the treating professional and/or team leader indicatingthat the patient failed to check-in as specified. An alert may also beprovided to the patient and other designated recipient with a request tocheck-in.

With reference to the example user interface illustrated in FIG. 4U, ifthe patient check-in option was selected, the check-in user interfacemay be configured to include fields that prompt the patient (or thepatient's caretaker) to indicate if the patient knows how the patientfeels, to describe how the patient feels, to indicate what treatment theuser feels is working in a beneficial manner, to indicate what treatmentthe user feels (e.g., subjectively feels) is not working in a beneficialmanner or is having an adverse effect, to indicate what the patientfeels (e.g., subjectively feels) is going or working well in thepatient's life, to indicate what is not going or working well in thepatient's life, what others do not know about what is going on with thepatient, how the patient feels physically, etc. Collecting and analyzingpatterns with respect to the patient's subjective sense on how thepatient is doing, what is working for the patient, and what is notworking for the patient can be very helpful in understanding andtreating the patient (e.g., sometimes as helpful or more helpful thanthe patient's clinical symptoms). Optionally, an analysis may beperformed to identify a frequency/clustering of a patient's subjectivefeelings of wellbeing or feelings of illness or lack of wellbeing. Theclustering (e.g., peaks of a certain subjective feeling over a period oftime) may then be utilized to identify current or predict future timeperiods that may be difficult for or result in a sense of a lack ofwellbeing on the part of the patient.

If the Significant Other/Caregiver/Family Member option was selected,the check-in user interface may be configured to include fields thatprompt the non-patient user to indicate how the patient is generallydoing, what are the user's most significant concerns regarding thepatient, how the user is feeling, what the user thinks the patient isnot telling the treating professional, what the user needs help with,etc.

The check-in section of the notebook may be configured to enablereal-time or recorded videos or images (optionally with an associatedvoice track) of the patient and/or significant other/caregiver/familymember to be transmitted to the treatment provider and/or support staffterminals to enable them to visually see and assess the patient and/orsignificant other/caregiver/family member. Such visual content mayprovide significant or critical information in making mental and/orphysical health assessments (e.g., enable the treatment provider todetect if someone has suffered a stroke or heart attack, or is sufferingfrom drug abuse). Optionally, some or all of the information providedvia the fields described above may in addition or instead be providedvia the visual content, optionally including a corresponding sound track(of the patient or non-patient speaking). The visual content mayoptionally be time-stamped indicating what day and time it was recordedand/or transmitted. A record control may be provided to initiate a videoor image recording via the camera on the user terminal.

FIG. 4V illustrates an example new information user interface. A userinterface may be provided enable a user to receive information about theuser's area of concern. The user may explicitly submit a description ofthe area of concern, select an area of concern from a menu provided viathe notebook, or the notebook or remote system may infer the area ofconcern from information received via one or more of the other notebooksections (e.g., based on the medical condition selected, the listsection, the referral section, the contacts section, the wall section,the treatment plan section, the medication section, the treatmentsection, etc.). The system will search for and access new informationcorresponding to the area of concern, and cause the new information tobe presented via the new information user interface. An item ofinformation may be categorized by the system as new if it has beenposted or otherwise made available no more than a specified thresholdperiod of time (e.g., the last 60 days) or since the user last accessedthe new information user interface. The new information may include awide variety of views and/or scientific opinion from a wide variety ofsources (e.g., institutions and people). Optionally, avalidation/credibility determination process may be performed for agiven item of new information prior to presenting the information viathe new information user interface.

FIG. 4W illustrates an example biographical user interface via which apatient can provide the patient's overall life story. The biographicaluser interface may include fields via which the patient can specify someor all of the following: ethnicity, where the patient's parents wereborn (e.g., country, state, city, etc.), if there were or are anyspecial problems in the patient's family of origin, if there were or areany health problems or illness in the patient's family of origin, wherethe patient was born (e.g., country, state, city, etc.), whether thepatient has any siblings and if so there gender, ages, if they arecurrently alive, cause of death and/or other details, if there werethere any deaths in your family that were unexplained, the places thepatient has lived since your birth (e.g., country, state, city, etc.),and/or other biographical information.

FIG. 4X illustrates an example financial (“money matters”) userinterface which may be used to indicate the source of payments (e.g.,private insurance, government funding, self-funding, etc.). Thefinancial section enables the patient (or non-patient) to recordinsurance information that will aid the person in submitting claims toan insurance company and in keeping track of what claims the insurancecompany has paid to-date and what claims need follow-up or additionalinformation.

The financial user interface may include fields via which some or all ofthe following may be specified: an indication as to whether the patienthas insurance, and if so the corresponding insurance information (e.g.,the identification number, Rx Bin, Rx PCN, Rx Group, Plan code, Groupnumber, etc.). The financial user interface may also prompt the user(the patient or non-patient user) to indicate whether the user wants tothe use the notebook for keeping track of insurance billing matters. Ifthe user responds affirmatively, the user may be prompted to provideclaim information (e.g., receipts, itemized bills, what the treatment orvisit was for, to whom is payment to be made, etc.).

The financial user interface may also prompt the user to indicatewhether the patient has disability coverage or Long Term DisabilityCoverage (LTD), and if so, provide related information (e.g., theinsurance provider, the policy number, etc.). If the user does have LTDcoverage, the financial user interface may also prompt the user toindicate whether the user wants to utilize the notebook to keep track ofthe patient's related claims. If the user indicates that the user wantsto utilize the notebook to keep track of the patient's LTD claims, theuser is requested to provide information regarding the claims (e.g.,evidence that the patient is disabled and the nature of the disability,such as a doctor's statement or form regarding the doctor's opinion onthe patient's condition, evidence that the patient had been employedwhen the disability occurred, evidence that any waiting period hasexpired, etc.).

The financial user interface may also prompt the user to indicatewhether the patient has Supplemental Security Income (SSI), and if so,to provide related information, such as the patient's income, thepatient's assets, the patient's living arrangements, the patient'scitizenship or alien status, the patient's health issues and how theyaffect the patient's daily activities and ability to work, etc. If theuser does have SSI, the financial user interface may also prompt theuser to indicate whether the user wants to utilize the notebook to keeptrack of the patient's related SSI claims. If the user indicates thatthe user wants to utilize the notebook to keep track of the patient'sSSI claims, the user is requested to provide information regarding theclaims.

The financial user interface may also prompt the user to indicatewhether the patient has Social Security Disability Insurance (SSDI), andif so, to provide related information, such as the patient's SocialSecurity number and proof of the patient's age, names, addresses andphone numbers of doctors, caseworkers, hospitals, and clinics that tookcare of the patient and the dates of appointments, names and dosages ofthe medications the patient is taking, medical records laboratory andtest results, a summary of where the patient worked and the kind of workthe patient did, the patient's most recent W-2 form or, ifself-employed, a copy of the patient's federal tax return, informationabout the patient's family members, Social Security numbers and proof ofage for each family member who may qualify for benefits, etc. If theuser does have SSDI, the financial user interface may also prompt theuser to indicate whether the user wants to utilize the notebook to keeptrack of the patient's related SSDI claims. If the user indicates thatthe user wants to utilize the notebook to keep track of the patient'sSSDI claims, the user is requested to provide information regarding theclaims.

A grid may be generated and displayed configured to aid in the trackingof claims and payments made to treatment providers, including thepayment amounts and payment dates. For example, the grid rows maycorrespond to respective treatment providers, and the columns maycorrespond to payment dates (or vice versa). A given grid cell may lista payment amount (e.g., a payment made or due). Thus, the grid mayprovide an “at a glance” summary of payments made and payments dueenabling a patient/caretaker or other user that has financialresponsibility with respect to the patient.

FIG. 4Y illustrates an example resources user interface configured toprovide a directory of resources (which may be in the form of linkedtext that can be activated to access more detailed information). Thedisplay of the resources may be organized by, diagnosis or cluster ofdiagnosis, type of specialty or need, etc. The resource user interfacemay also include a search field enabling the user also be used to searchfor and/or display resources from the resource directory depending uponthe patient's geographical needs (e.g., within a specified region, city,zip code, a specific number of miles from the patient's residence and/orfrom the device hosting the notebook, etc.).

FIG. 4Z illustrates an example team user interface configured to enablea support team to be defined for a patient. For example, the team userinterface may include fields via which names may be added (e.g., via acontact database) for members of the team and where tasks may beassociated with a given team member. Example tasks may include providingtransportation for the patient to medical appointments, providing mealsfor the patient, following-up with the patient to ensure the patient istaking the prescribed medication and performing the prescribed therapy,etc. A given team member may be designated as a team leader. The teamleader may be automatically informed of patient-related events enteredinto the notebook, such as medical tests (e.g., scans, blood tests,biopsies, etc.) and test results, admissions to hospitals, medicalreferrals, newly prescribed medications, termination of medications,newly prescribed therapies (e.g., physical therapy, speech therapy,counseling sessions, etc.), termination of therapies, changes in thepatient's living situation (e.g., the patient has moved, some new isliving with the patient, etc.), etc. This enables the team leader to bemore informed regarding the patient's changing situation, to comment onsuch changes, and to communicate with the patient, the patient's medicalprofessionals, the patient's family, the patient's caretaker, other teammembers, etc., regarding the changes and potential actions that shouldbe taken.

FIG. 3B illustrates an example process for identifying alert conditionsusing natural language processing and keyword identification based onuser input. At block 301B, the user is authenticated as similarlydescribed above using facial recognition on a captured image of the useror by scanning and comparing the user's fingerprint. The user input maybe provided via voice, touch (e.g., via a human digit or stylus),keyboard, a combination of two or more of the foregoing, or otherwise.If user input is being received as a voice input (spoken words) viamicrophone, than at block 302B, the voice input is received and at block304B, speech-to-text conversion is performed (e.g., by the user terminaland/or by a remote system). As discussed elsewhere herein, thespeech-to-text conversion process may be performed using one or more ofpattern matching, pattern and feature analysis, language modeling andstatistical analysis, and/or neural networks. Optionally,speaker-adaptive, continuous speech recognition may be utilized inconverting speech to text.

At block 306B, natural language processing is optionally performed onthe user input (e.g., touch input, keyboard input, or the text generatedby the speech-to-text process). At block 308B, keyword identification isperformed (e.g., keywords that indicate the topic of the user input orthat indicate an emotion or feeling of wellbeing). At block 310B adetermination is made as to whether the identified keywords in the userinput indicate a critical/safety related condition. The keywordcriticality determination may be performed by comparing the user inputagainst a data store of keywords that indicate a potential criticalcondition. For example, the keyword data store may include some or allof the following keywords (or key phrases): hopeless, worthless,suicidal, anxious, depressed, afraid, helpless, afraid, out-of-control,gun, knife, rage, furious, violent, drinking, drunk, drugged, scream,out-to-get-me, etc. A given keyword may be associated with a conditiontype, such as a psychological condition, a pharmaceutical condition, anorthopedic condition, etc. Optionally, a critically determination mayweight different keywords differently, and the criticality determinationmay optionally calculate a criticality score based on the number ofkeywords and the keyword weighting. If the criticality score exceeds aspecified threshold, a determination may be made that a potentialcritical condition. For example, the following formula may be used:

Criticality Score=Weght¹ (of Keyword¹)+Weght² (of Keyword²) . . .+Weght^(n) (of Keyword^(n))

Where a potential critical condition exists if CriticalityScore≥Criticality Score

If the keyword criticality determination identifies a potential criticalcondition, at block 312B, an alert may be dynamically generated andtransmitted to one or more destinations based on one or more rulesaccessed from a rule data store. For example, a rule may indicate thatall alerts are to be transmitted to a previously identifiedcaretaker/family member and a previously identified primary physician.Another rule may indicate that if a keyword is associated with aphysiological condition, then an alert is to be transmitted to aspecified psychiatrist or psychologist.

Thus, processes and techniques are described that may be used toreceive, manage and process the recording, arrangement, text processing,word recognition, and/or review of information for or in an electronicnotebook.

The methods and processes described herein may have fewer or additionalsteps or states and the steps or states may be performed in a differentorder. Not all steps or states need to be reached. The methods andprocesses described herein may be embodied in, and fully or partiallyautomated via, software code modules executed by one or more generalpurpose computers. The code modules may be stored in any type ofcomputer-readable medium or other computer storage device. Some or allof the methods may alternatively be embodied in whole or in part inspecialized computer hardware. The systems described herein mayoptionally include displays, user input devices (e.g., touchscreen,keyboard, mouse, voice recognition, etc.), network interfaces, etc.

The results of the disclosed methods may be stored in any type ofcomputer data repository, such as relational databases and flat filesystems that use volatile and/or non-volatile memory (e.g., magneticdisk storage, optical storage, EEPROM and/or solid state RAM).

The various illustrative logical blocks, modules, routines, andalgorithm steps described in connection with the embodiments disclosedherein can be implemented as electronic hardware, computer software, orcombinations of both. To clearly illustrate this interchangeability ofhardware and software, various illustrative components, blocks, modules,and steps have been described above generally in terms of theirfunctionality. Whether such functionality is implemented as hardware orsoftware depends upon the particular application and design constraintsimposed on the overall system. The described functionality can beimplemented in varying ways for each particular application, but suchimplementation decisions should not be interpreted as causing adeparture from the scope of the disclosure.

Moreover, the various illustrative logical blocks and modules describedin connection with the embodiments disclosed herein can be implementedor performed by a machine, such as a general purpose processor device, adigital signal processor (DSP), an application specific integratedcircuit (ASIC), a field programmable gate array (FPGA) or otherprogrammable logic device, discrete gate or transistor logic, discretehardware components, or any combination thereof designed to perform thefunctions described herein. A general purpose processor device can be amicroprocessor, but in the alternative, the processor device can be acontroller, microcontroller, or state machine, combinations of the same,or the like. A processor device can include electrical circuitryconfigured to process computer-executable instructions. In anotherembodiment, a processor device includes an FPGA or other programmabledevice that performs logic operations without processingcomputer-executable instructions. A processor device can also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration. Although described herein primarily with respect todigital technology, a processor device may also include primarily analogcomponents. A computing environment can include any type of computersystem, including, but not limited to, a computer system based on amicroprocessor, a mainframe computer, a digital signal processor, aportable computing device, a device controller, or a computationalengine within an appliance, to name a few.

The elements of a method, process, routine, or algorithm described inconnection with the embodiments disclosed herein can be embodieddirectly in hardware, in a software module executed by a processordevice, or in a combination of the two. A software module can reside inRAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory,registers, hard disk, a removable disk, a CD-ROM, or any other form of anon-transitory computer-readable storage medium. An exemplary storagemedium can be coupled to the processor device such that the processordevice can read information from, and write information to, the storagemedium. In the alternative, the storage medium can be integral to theprocessor device. The processor device and the storage medium can residein an ASIC. The ASIC can reside in a user terminal. In the alternative,the processor device and the storage medium can reside as discretecomponents in a user terminal.

Conditional language used herein, such as, among others, “can,” “may,”“might,” “may,” “e.g.,” and the like, unless specifically statedotherwise, or otherwise understood within the context as used, isgenerally intended to convey that certain embodiments include, whileother embodiments do not include, certain features, elements and/orsteps. Thus, such conditional language is not generally intended toimply that features, elements and/or steps are in any way required forone or more embodiments or that one or more embodiments necessarilyinclude logic for deciding, with or without other input or prompting,whether these features, elements and/or steps are included or are to beperformed in any particular embodiment. The terms “comprising,”“including,” “having,” and the like are synonymous and are usedinclusively, in an open-ended fashion, and do not exclude additionalelements, features, acts, operations, and so forth. Also, the term “or”is used in its inclusive sense (and not in its exclusive sense) so thatwhen used, for example, to connect a list of elements, the term “or”means one, some, or all of the elements in the list.

Disjunctive language such as the phrase “at least one of X, Y, Z,”unless specifically stated otherwise, is otherwise understood with thecontext as used in general to present that an item, term, etc., may beeither X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z).Thus, such disjunctive language is not generally intended to, and shouldnot, imply that certain embodiments require at least one of X, at leastone of Y, or at least one of Z to each be present.

While the phrase “click” may be used with respect to a user selecting acontrol, menu selection, or the like, other user inputs may be used,such as voice commands, text entry, gestures, etc. User inputs may, byway of example, be provided via an interface, such as via text fields,wherein a user enters text, and/or via a menu selection (e.g., a dropdown menu, a list or other arrangement via which the user can check viaa check box or otherwise make a selection or selections, a group ofindividually selectable icons, etc.). When the user provides an input oractivates a control, a corresponding computing system may perform thecorresponding operation. Some or all of the data, inputs andinstructions provided by a user may optionally be stored in a systemdata store (e.g., a database), from which the system may access andretrieve such data, inputs, and instructions. The notifications/alertsand user interfaces described herein may be provided via a Web page, adedicated or non-dedicated phone application, computer application, ashort messaging service message (e.g., SMS, MMS, etc.), instantmessaging, email, push notification, audibly, a pop-up interface, and/orotherwise.

The user terminals described herein may be in the form of a mobilecommunication device (e.g., a cell phone), laptop, tablet computer,interactive television, game console, media streaming device,head-wearable display, networked watch, etc. The user terminals mayoptionally include displays, user input devices (e.g., touchscreen,keyboard, mouse, voice recognition, etc.), network interfaces, etc.

While the above detailed description has shown, described, and pointedout novel features as applied to various embodiments, it can beunderstood that various omissions, substitutions, and changes in theform and details of the devices or algorithms illustrated can be madewithout departing from the spirit of the disclosure. As can berecognized, certain embodiments described herein can be embodied withina form that does not provide all of the features and benefits set forthherein, as some features can be used or practiced separately fromothers. The scope of certain embodiments disclosed herein is indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. (canceled)
 2. A wireless mobile communication system of a user, thewireless mobile communication system comprising: a processor device; anon-transitory computer readable medium that stores instructions thatwhen executed by the processor device cause the processor device toperform operations comprising: establishing an encrypted transmissionover a wireless network between the communication system and a cloudsystem using a secure transfer mechanism; authenticating a user using animage of the user captured using a camera of the wireless mobilecommunication system, and/or authenticating the user using a scan of afingerprint of the user using a fingerprint scanner of the wirelessmobile communication system, wirelessly accessing and decrypting, usingthe secure transfer mechanism, encrypted medical data regarding the userfrom a plurality of encrypted sources stored on the cloud system,wherein the user is a patient; providing for display a user diaryinterface comprising one or more fields which receive from the user anongoing chronology of appointments for the user, interventions for theuser, testing for the user, including associated dates; accessing a userdiary comprising encrypted data entered by the user using the user diaryinterface and stored on the wireless communication system; causing, atleast in part, a non-linear patient health timeline user interfacerendering to be generated of at least a portion of the user encryptedmedical data from the plurality of encrypted sources, the non-linearpatient health timeline zoomable in response to a gesture made using twofingers, the non-linear patient health timeline comprising: medicalappointment entries, medical diagnosis entries, and treatment entries;at least a portion of the user-entered data from the user diary, whereinthe user is the patient; recording in wireless mobile communicationsystem memory new medical data regarding the user; synchronizing the newmedical data recorded in the wireless mobile communication system memorywith user encrypted medical data stored on the cloud system; causing, atleast in part, the non-linear patient health timeline to be updated withthe recorded new medical data, wherein the recorded new medical data isvisually emphasized relative to other data in the non-linear patienthealth timeline; causing, at least in part, an entry, corresponding to afirst calendar entry, to be displayed via the non-linear patient healthtimeline; receiving referral contact information for a first medicalprovider that the user is being referred to; automatically augmenting atleast one calendar entry for the user, wherein the user is the patient,with at least a portion of the referral contact information of the firstmedical provider that the user is being referred to; and enabling thereferral contact information to be added to a contact database of theuser.
 3. The wireless mobile communication system as defined in claim 2,the operations further comprising: accessing user data comprising:diagnosis dates, medical intervention dates, enabling the non-linearpatient health timeline to be generated with entries corresponding to atleast a portion of the accessed user data, the non-linear patient healthtimeline comprising: medical appointment entries, medical diagnosisentries, and treatment entries; at least a portion of the user-entereddata from the user diary, wherein the user is the patient; detecting auser selection of an item from a plurality of items on the generatednon-linear patient health timeline; and causing additional informationregarding the non-linear patient health timeline item selection to bepresented.
 4. The wireless mobile communication system as defined inclaim 2, the operations further comprising: generating a data sharinguser interface, the data sharing user interface comprising: a searchfield; a search filter user interface; a posting field; a tag field; afavorite control that enables the user to designate a posting or aposting user as a favorite; posting information received via the postingfield; tagging the posted information using a tag received via the tagfield; conducting, using the cloud system, a search using a user searchquery received via the search field and one or more user-selectedpredefined search filters selected by the user using the search filteruser interface, the user-selected predefined search filters comprisingone or more medical diagnosis or medical conditions; and providingsearch results filtered in accordance with the user-selected one or moresearch filters for display.
 5. The wireless mobile communication systemas defined in claim 2, the operations further comprising: generating acalendar entry for a second medical appointment; recording audio contentrelated to the second medical appointment using a microphone of thecommunication system; transmitting the audio content to the cloud systemusing the secure transfer mechanism; using the cloud system to perform anatural language processing process comprising language modeling andstatistical analysis to convert the audio content to text; and addingthe text, one or more medical test results, and one or moreprescriptions to the calendar entry for the second medical appointment.6. The wireless mobile communication system as defined in claim 2, theoperations further comprising: recording audio content of a medicalprofessional at a second medical appointment; transmitting the audiocontent to the cloud system using the secure transfer mechanism; usingthe cloud system to perform a natural language processing processcomprising language modeling and statistical analysis to convert theaudio content of the medical professional to text; determining, usingthe cloud system, if the text includes a recommendation; and at leastpartly in response to a determination that the text includes therecommendation, adding the recommendation to an electronic to-do list.7. The wireless mobile communication system as defined in claim 2, theoperations further comprising: generating a calendar entry for a secondmedical appointment; recording video and audio content related to thesecond medical appointment using the communication system camera and amicrophone; associating a timestamp with the recorded video and audiocontent; and adding the video and audio content to the calendar entryfor the second medical appointment.
 8. The wireless mobile communicationsystem as defined in claim 2, wherein the cloud system performsoperations comprising: encrypt user data received by the cloud system;storing the encrypted user data in a first storage system; and storing akey associated with the encrypted user data to be stored on a secondstorage system physically separate from the first storage system.
 9. Thewireless mobile communication system as defined in claim 2, theoperations further comprising: converting, using the cloud system, avoice input from voice to text using a natural language processingprocess, the natural language processing process comprising determininga probability of certain words or sounds following one from one anotherto thereby speed up word recognition and improve recognition accuracy.10. The wireless mobile communication system as defined in claim 2, theoperations further comprising: converting, using the cloud system, avoice input from voice to text via a natural language processing systemcomprising a neural networking trained to recognize patterns comprisingword sounds to improve the natural language processing system's abilityto understand the voice input.
 11. The wireless mobile communicationsystem as defined in claim 2, wherein the cloud system is configured toperform operations comprising: providing a team user interface thatenables: a medical team comprising a plurality of team members to bedefined for the user; respective tasks to be associated with respectivemembers of the medical team; a designation of a team leader; receiving,via the team user interface, a medical team definition and a team leaderdesignation; using at least one voice input from the user in detecting afirst user condition; enabling an alert, including text corresponding toat least a portion of the voice input from the user, to be transmittedto at least the designated team leader; and enabling members of thedefined medical team to communicate with each other and access datarelated to the user.
 12. The wireless mobile communication system asdefined in claim 2, wherein the referral contact information for a firstmedical provider comprises a phone number, a physical address, andspecialty information.
 13. The wireless mobile communication system asdefined in claim 2, the operations further comprising: detecting a userselection of the first medical appointment entry on the non-linearpatient health timeline; and in response to detecting the user selectionof the first medical appointment entry on the non-linear patient healthtimeline, opening and displaying the corresponding first calendar entry,including time, date, and location information.
 14. The wireless mobilecommunication system as defined in claim 2, the operations furthercomprising: in response to receiving a user zoom instruction on thenon-linear patient health timeline to select a first portion of thetimeline, the user zoom instruction comprising a first gesture, causingthe first portion of the non-linear patient health timeline to bedisplayed at a first resolution in a first region together with adisplay of the non-linear patient health timeline at a second resolutiondisplayed in a second region separate from the first region.
 15. Acomputer implemented method, the method comprising: establishing, usinga network interface of a wireless mobile computer system of a user, theuser being a patient, an encrypted transmission over a wireless networkbetween the wireless mobile computer system and a cloud system using asecure transfer mechanism; using the wireless mobile computer system to:authenticate the user using an image of the user captured using awireless mobile computer system camera, and/or authenticate the userusing a scan of a fingerprint of the user using a wireless mobilecomputer system fingerprint scanner; causing, at least in part, thewireless mobile computer system to wirelessly access, using the securetransfer mechanism, and decrypt encrypted medical data regarding theuser from a plurality of encrypted sources stored on the cloud system;causing, at least in part, a non-linear timeline user interface to begenerated displaying, on the wireless mobile computer system, at least aportion of the user encrypted medical data from the plurality ofencrypted sources, the non-linear timeline providing an overview of atleast a portion of a medical history of the user, the non-lineartimeline zoomable in response to a user instruction, the non-lineartimeline comprising: medical appointment entries, medical diagnosisentries, and treatment entries; recording new medical data on thewireless mobile computer system; utilizing the secure transfer mechanismto wirelessly synchronize the recorded new medical data on the wirelessmobile computer system with data stored on the cloud system; enablingthe non-linear timeline to be updated with the new medical data, whereinthe new medical data is visually emphasized relative to other data inthe non-linear timeline; storing a first calendar entry associated witha first medical appointment associated with a first medical appointmenttiming; automatically augmenting at least one calendar entry for theuser, wherein the user is the patient, with at least a portion ofreferral contact information of a first medical provider that the useris being referred to; and enabling referral contact information to beadded to a contact database of the user.
 16. The method as defined inclaim 15, the method further comprising: receiving at the cloud system atask; identifying a source of data associated with the task; andassigning the task to a cloud node based at least in part on a geoproximity of the cloud node to the source of data associated with thetask.
 17. The method as defined in claim 15, the method furthercomprising: encrypting user data using the cloud system; storing theencrypted user data in a first storage system; and storing a keyassociated with the encrypted user data store on the first storagesystem on a second storage system physically separate from the firststorage system.
 18. The method as defined in claim 15, the methodfurther comprising: detecting, using the wireless mobile computersystem, a user selection of the first medical appointment entry on thenon-linear timeline; and in response to detecting the user selection ofthe first medical appointment entry on the non-linear timeline, openingand displaying the corresponding first calendar entry, including time,date, and location information on the wireless mobile computer system.19. The method as defined in claim 15, the method further comprising: inresponse to receiving, using the wireless mobile computer system, a userzoom instruction on the non-linear timeline to select a first portion ofthe non-linear timeline, the user zoom instruction comprising a firstgesture, causing the first portion of the non-linear timeline to bedisplayed at a first resolution in a first region together with adisplay of the non-linear timeline at a second resolution displayed in asecond region separate from the first region.